Skip to content

Add Warning Messages for Adaptive QoS#8

Merged
ExtremeFiretop merged 3 commits intodevelopfrom
Adaptive-QoS
Jun 8, 2025
Merged

Add Warning Messages for Adaptive QoS#8
ExtremeFiretop merged 3 commits intodevelopfrom
Adaptive-QoS

Conversation

@ExtremeFiretop
Copy link
Member

@ExtremeFiretop ExtremeFiretop commented Jun 7, 2025

Add Warning Messages for Adaptive QoS
If Adaptive QoS is not functional, display a warning message to the user in shell and the WebUI

image

image

Add Warning Messages for Adaptive QoS
If Adaptive QoS is not functional, display a warning message to the user in shell and the WebUI
@ExtremeFiretop ExtremeFiretop requested review from a team as code owners June 7, 2025 22:23
Ignore annoying Shellcheck
Ignore Shellcheck x2
@dave14305
Copy link

I’m not spending time approving PRs to the develop branch. Why does the develop branch exist?

@ExtremeFiretop
Copy link
Member Author

ExtremeFiretop commented Jun 8, 2025

I’m not spending time approving PRs to the develop branch. Why does the develop branch exist?

To each their own. The question has been answered multiple times though in the discussions. Develop is used as a middle point between production and the rest of the team.

You already identified that the PR against master was not worth a new release. Well unless you want every teams members PR to be a new release. You need a place to commit those PRs too as a middle ground; called develop. Else the only choice is to commit against master.

@ExtremeFiretop ExtremeFiretop merged commit 0831d46 into develop Jun 8, 2025
2 checks passed
@ExtremeFiretop ExtremeFiretop deleted the Adaptive-QoS branch June 8, 2025 02:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments